[do not merge] Test out package name differing from project name#21
[do not merge] Test out package name differing from project name#21
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
11 Skipped Deployments
|
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
There was a problem hiding this comment.
Additional Suggestion:
The turbo filter commands in vercel.json reference the old package name "nextjs-pages-blog", but the package.json name was changed to "nextjs-pages-blog-different-than-vercel-project-name". This will cause build and install commands to fail on Vercel because turbo filters match against the actual package name.
View Details
📝 Patch Details
diff --git a/examples/nextjs-pages/blog/vercel.json b/examples/nextjs-pages/blog/vercel.json
index 60025d1..fa1d12f 100644
--- a/examples/nextjs-pages/blog/vercel.json
+++ b/examples/nextjs-pages/blog/vercel.json
@@ -1,4 +1,4 @@
{
- "buildCommand": "pnpm --workspace-root exec turbo --no-daemon --filter nextjs-pages-blog build --env-mode loose",
- "installCommand": "node -v && pnpm --workspace-root --filter nextjs-pages-blog... install --config.dedupe-peer-dependents=false"
+ "buildCommand": "pnpm --workspace-root exec turbo --no-daemon --filter nextjs-pages-blog-different-than-vercel-project-name build --env-mode loose",
+ "installCommand": "node -v && pnpm --workspace-root --filter nextjs-pages-blog-different-than-vercel-project-name... install --config.dedupe-peer-dependents=false"
}
Analysis
Turbo filter mismatch in vercel.json causes build failures on Vercel
What fails: Deployment to Vercel fails because vercel.json contains turbo filters that don't match the package name in package.json. The build command --filter nextjs-pages-blog cannot locate the package named nextjs-pages-blog-different-than-vercel-project-name.
How to reproduce:
- Deploy the
examples/nextjs-pages/blogapplication to Vercel - Vercel executes the buildCommand:
pnpm --workspace-root exec turbo --no-daemon --filter nextjs-pages-blog build --env-mode loose - Turbo uses exact name matching per Turbo's filtering documentation and looks for a package named exactly
nextjs-pages-blog
Result: Build fails with error indicating the filter cannot find the target package, because the actual package name in examples/nextjs-pages/blog/package.json is nextjs-pages-blog-different-than-vercel-project-name (not nextjs-pages-blog).
Expected: The turbo filters in vercel.json must match the name field in package.json. According to Turbo's filtering RFC, filters use "exact package name" matching: "To select an exact package, just specify its name."
Fix: Updated both filter references in vercel.json lines 2-3 from nextjs-pages-blog to nextjs-pages-blog-different-than-vercel-project-name to match the actual package name.
1 participant
No description provided.